feat(ai): add llms-full.txt shards for 5 projects missing AI discoverability#44
feat(ai): add llms-full.txt shards for 5 projects missing AI discoverability#44VaultSparkStudios wants to merge 1 commit into
Conversation
…ability Five active projects (Signal Log, Vault Pipeline, Vault Member, Obelisk, The Living Protocol) had working public pages but zero AI-readable content. These projects were invisible to AI crawlers reading /.well-known/llms.txt because neither their shards nor index entries existed (CANON-048 gap). Adds llms-full.txt for each project following the established format (identity, current focus, next milestone, cite instruction, studio context) and registers all five in /.well-known/llms.txt, growing the index from 18 to 23 shards. Co-Authored-By: Claude <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fce1c1d045
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - [Signal Log](https://vaultsparkstudios.com/projects/signal-log/llms-full.txt) — journal · sparked | ||
| - [Vault Pipeline](https://vaultsparkstudios.com/projects/vault-pipeline/llms-full.txt) — tool · sparked | ||
| - [Vault Member](https://vaultsparkstudios.com/projects/vault-member/llms-full.txt) — platform · sparked | ||
| - [Obelisk](https://vaultsparkstudios.com/projects/obelisk/llms-full.txt) — app · forge | ||
| - [The Living Protocol](https://vaultsparkstudios.com/projects/the-living-protocol/llms-full.txt) — app · forge |
There was a problem hiding this comment.
Adding these five shard links only to /.well-known/llms.txt breaks the AI-discovery spine because agents.json still advertises the previous 18 shard URLs. I checked this repo with node scripts/check-ai-discovery-spine.mjs; it now fails with a shard count mismatch and reports each of these new URLs as missing from agents.json, so npm run build:check will fail until the manifest/generated source is updated in the same change.
Useful? React with 👍 / 👎.
2 participants
Summary
Five active projects had working public pages but were completely invisible to AI crawlers — no
llms-full.txtshard and no entry in/.well-known/llms.txt. This is a CANON-048 gap (dual-audience: Humans AND AI Agents).Projects fixed:
journal · sparked) — dev journal; live at/journal/tool · sparked) — public development roadmap; live at/projects/vault-pipeline/platform · sparked) — cross-game identity/progress layer; live at/vault-member/app · forge) — unified identity and trust protocol; page at/projects/obelisk/app · forge) — generational wellness OS; page at/projects/the-living-protocol/Changes:
projects/{slug}/llms-full.txtfor each of the 5 projects, following the established format (identity, current focus, next milestone, cite instruction, studio context)/.well-known/llms.txtto register all 5 shards — index grows from 18 → 23 shardsRationale
Any AI agent or LLM reading
/.well-known/llms.txtto understand the VaultSpark ecosystem would have seen these projects listed in the nav and public pages but found zero machine-readable content about them. Vault Member in particular is the studio's core membership platform — its absence from AI-readable surfaces meant AI tools had no authoritative facts to cite.What to verify
https://vaultsparkstudios.com/.well-known/llms.txtafter deploy — should show 23 entrieshttps://vaultsparkstudios.com/projects/vault-member/llms-full.txt)scripts/build-llms-full-shards.mjsis used to regenerate shards, add these 5 projects to its project list so they stay in sync on future runsGenerated by Claude Code